Fixed visiblity of text on teh sponsors page dark mode #464

Adez017 · 2025-08-29T14:28:03Z

Description

now the text is clearly visible on the page with enhance fixes

Fixes #458

Type of Change

New feature (e.g., new page, component, or functionality)
Bug fix (non-breaking change that fixes an issue)
UI/UX improvement (design, layout, or styling updates)
Performance optimization (e.g., code splitting, caching)
Documentation update (README, contribution guidelines, etc.)
Other (please specify):

Changes Made

Updated css file

Dependencies

List any new dependencies or tools required for this change.
Mention any version updates or configurations that need to be considered.

Checklist

My code follows the style guidelines of this project.
I have tested my changes across major browsers/devices
My changes do not generate new console warnings or errors , I ran npm run build and attached scrrenshot in this PR.
This is already assigned Issue to me, not an unassigned issue.

##Screenshots

vercel · 2025-08-29T14:28:08Z

@Adez017 is attempting to deploy a commit to the recode Team on Vercel.

A member of the Team first needs to authorize it.

github-actions · 2025-08-29T14:28:11Z

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. The estimated time for response is 5–8 hrs.

In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, a video recording, or an image of the update you made below, which helps speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your PR goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent 20 contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Your perks for contribution to this community 👇🏻

Get free Consultation use code recode50 to get free: Mentorship for free.
Get the Ebook for free use code recode at checkout: Data Science cheatsheet for Beginners.
Check out this weekly Newsletter: Sanjay's Newsletter.

If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

iitzIrFan

@Adez017 I see that, you had changed the txt colours but, Can you add something in the bg to differentiate it from the rest to improve UX ?

Adez017 · 2025-08-30T03:22:13Z

@Adez017 I see that, you had changed the txt colours but, Can you add something in the bg to differentiate it from the rest to improve UX ?

Hi @iitzIrFan , i appreciate that but i think we dont need it as far as visiblity concern i had made sure that when the pop up shows in the other background should a little blur that make it easy to read the pop up . i am attaching a video let me if if still needed that change

Screen.Recording.2025-08-30.084900.mp4

iitzIrFan

LGTM ! @Adez017
@sanjay-kv Ready for Merge.

Adez017 · 2025-09-02T09:36:36Z

As of the new PR #465 , we loose the functionality of the previous card add your name here so this PR got invalid,
If you think we still need that card i think we need to made some changes to be revert . Also i noticed previously we had both theme light and dark workign on this page , now we lost the functionality. to be honest as a contributing member for now abuot one month i think the previous is more good in the UX and also its well modularised . what do you think @iitzIrFan @sanjay-kv

iitzIrFan · 2025-09-02T10:50:12Z

As of the new PR #465 , we loose the functionality of the previous card add your name here so this PR got invalid, If you think we still need that card i think we need to made some changes to be revert . Also i noticed previously we had both theme light and dark workign on this page , now we lost the functionality. to be honest as a contributing member for now abuot one month i think the previous is more good in the UX and also its well modularised . what do you think @iitzIrFan @sanjay-kv

@sanjay-kv Needs your thoughts on this !

sanjay-kv

awesome.

vercel · 2025-09-02T12:50:24Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
recode-website	Error			Sep 2, 2025 5:08pm

Adez017 · 2025-09-02T13:54:54Z

awesome.

Hi @sanjay-kv , i think you missed this : #464 (comment)

sanjay-kv · 2025-09-02T17:10:08Z

can u look into the build fail

[00:08:14.282] Running build in Washington, D.C., USA (East) – iad1 [00:08:14.282] Build machine configuration: 4 cores, 8 GB [00:08:14.303] Cloning github.com/recodehive/recode-website (Branch: docs, Commit: a123b89) [00:08:16.284] Cloning completed: 1.981s [00:08:22.224] Restored build cache from previous deployment (6JcRofLbrZVXAG2XSA3a2W95xd4e) [00:08:23.114] Running "vercel build" [00:08:23.517] Vercel CLI 46.1.1 [00:08:24.127] Warning: Detected "engines": { "node": ">=18.0" } in your package.jsonthat will automatically upgrade when a new major Node.js Version is released. Learn More: http://vercel.link/node-version [00:08:24.131] Installing dependencies... [00:08:26.917] [00:08:26.918] up to date in 3s [00:08:26.918] [00:08:26.918] 422 packages are looking for funding [00:08:26.918] runnpm fund for details [00:08:26.960] Running "npm run build" [00:08:27.075] [00:08:27.076] > [email protected] build [00:08:27.076] > docusaurus build [00:08:27.076] [00:08:28.447] [INFO] [en] Creating an optimized production build... [00:08:29.007] [WARNING] Docusaurus found blog posts without truncation markers: [00:08:29.007] - "blog/spark-architecture/index.md" [00:08:29.007] - "blog/git-coding-agent/index.md" [00:08:29.007] - "blog/ux-ui-design-job/index.md" [00:08:29.008] - "blog/ux-designers-ai/index.md" [00:08:29.008] - "blog/streamline-ux-ui/index.md" [00:08:29.008] - "blog/google-deepmind/index.md" [00:08:29.008] - "blog/google-backlinks/index.md" [00:08:29.008] [00:08:29.008] We recommend using truncation markers (or{/* truncate */}) in blog posts to create shorter previews on blog paginated lists. [00:08:29.008] Tip: turn this security off with the onUntruncatedBlogPosts: 'ignore' blog plugin option. [00:08:29.605] [info] [webpackbar] Compiling Client [00:08:29.640] [info] [webpackbar] Compiling Server [00:08:41.004] [success] [webpackbar] Server: Compiled successfully in 11.36s [00:08:52.361] [success] [webpackbar] Client: Compiled with some errors in 22.76s [00:08:52.366] [ERROR] Client bundle compiled with errors therefore further build is impossible. [00:08:52.367] Syntax error: /vercel/path0/src/pages/our-sponsors/Sponsors.css Unclosed block (621:1) [00:08:52.367] [00:08:52.367] �[90m 619 | �[39m line-height�[33m:�[39m 1.6�[33m;�[39m [00:08:52.367] �[90m 620 | �[39m�[33m}�[39m [00:08:52.367] �[1m�[31m>�[39m�[22m�[90m 621 | �[39m�[33m[�[39mdata-theme=�[32m'dark'�[39m�[33m]�[39m �[33m.scanner-content�[39m �[33m{�[39m [00:08:52.367] �[90m | �[39m�[1m�[31m^�[39m�[22m [00:08:52.367] �[90m 622 | �[39m background�[33m:�[39m �[36mvar�[39m�[36m(--dark-bg-secondary)�[39m�[33m;�[39m [00:08:52.368] �[90m 623 | �[39m color�[33m:�[39m �[36mvar�[39m�[36m(--dark-text-primary)�[39m�[33m;�[39m [00:08:52.368] [00:08:52.368] -------------------------- [00:08:52.368] [00:08:52.368] Syntax error: /vercel/path0/src/pages/our-sponsors/Sponsors.css Unclosed block (621:1) [00:08:52.368] [00:08:52.368] �[90m 619 | �[39m line-height�[33m:�[39m 1.6�[33m;�[39m [00:08:52.368] �[90m 620 | �[39m�[33m}�[39m [00:08:52.368] �[1m�[31m>�[39m�[22m�[90m 621 | �[39m�[33m[�[39mdata-theme=�[32m'dark'�[39m�[33m]�[39m �[33m.scanner-content�[39m �[33m{�[39m [00:08:52.368] �[90m | �[39m�[1m�[31m^�[39m�[22m [00:08:52.368] �[90m 622 | �[39m background�[33m:�[39m �[36mvar�[39m�[36m(--dark-bg-secondary)�[39m�[33m;�[39m [00:08:52.368] �[90m 623 | �[39m color�[33m:�[39m �[36mvar�[39m�[36m(--dark-text-primary)�[39m�[33m;�[39m [00:08:52.368] -- inner error -- [00:08:52.368] [00:08:52.368] Syntax error: /vercel/path0/src/pages/our-sponsors/Sponsors.css Unclosed block (621:1) [00:08:52.368] [00:08:52.368] �[90m 619 | �[39m line-height�[33m:�[39m 1.6�[33m;�[39m [00:08:52.368] �[90m 620 | �[39m�[33m}�[39m [00:08:52.369] �[1m�[31m>�[39m�[22m�[90m 621 | �[39m�[33m[�[39mdata-theme=�[32m'dark'�[39m�[33m]�[39m �[33m.scanner-content�[39m �[33m{�[39m [00:08:52.369] �[90m | �[39m�[1m�[31m^�[39m�[22m [00:08:52.369] �[90m 622 | �[39m background�[33m:�[39m �[36mvar�[39m�[36m(--dark-bg-secondary)�[39m�[33m;�[39m [00:08:52.369] �[90m 623 | �[39m color�[33m:�[39m �[36mvar�[39m�[36m(--dark-text-primary)�[39m�[33m;�[39m [00:08:52.369] Generated code for /vercel/path0/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[7].use[1]!/vercel/path0/node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[7].use[2]!/vercel/path0/src/pages/our-sponsors/Sponsors.css [00:08:52.443] Error: Command "npm run build" exited with 1

Adez017 · 2025-09-02T17:10:20Z

what are your thoughts @sanjay-kv ?
#464 (comment)

The deploymenton will fail as mentioned in the above command , will need your thoughts and approval whether keep those changes or revert back

Adez017 · 2025-09-02T17:10:56Z

can u look into the build fail

[00:08:14.282] Running build in Washington, D.C., USA (East) – iad1 [00:08:14.282] Build machine configuration: 4 cores, 8 GB [00:08:14.303] Cloning github.com/recodehive/recode-website (Branch: docs, Commit: a123b89) [00:08:16.284] Cloning completed: 1.981s [00:08:22.224] Restored build cache from previous deployment (6JcRofLbrZVXAG2XSA3a2W95xd4e) [00:08:23.114] Running "vercel build" [00:08:23.517] Vercel CLI 46.1.1 [00:08:24.127] Warning: Detected "engines": { "node": ">=18.0" } in your package.jsonthat will automatically upgrade when a new major Node.js Version is released. Learn More: http://vercel.link/node-version [00:08:24.131] Installing dependencies... [00:08:26.917] [00:08:26.918] up to date in 3s [00:08:26.918] [00:08:26.918] 422 packages are looking for funding [00:08:26.918] runnpm fund for details [00:08:26.960] Running "npm run build" [00:08:27.075] [00:08:27.076] > [email protected] build [00:08:27.076] > docusaurus build [00:08:27.076] [00:08:28.447] [INFO] [en] Creating an optimized production build... [00:08:29.007] [WARNING] Docusaurus found blog posts without truncation markers: [00:08:29.007] - "blog/spark-architecture/index.md" [00:08:29.007] - "blog/git-coding-agent/index.md" [00:08:29.007] - "blog/ux-ui-design-job/index.md" [00:08:29.008] - "blog/ux-designers-ai/index.md" [00:08:29.008] - "blog/streamline-ux-ui/index.md" [00:08:29.008] - "blog/google-deepmind/index.md" [00:08:29.008] - "blog/google-backlinks/index.md" [00:08:29.008] [00:08:29.008] We recommend using truncation markers (``or{/* truncate */}) in blog posts to create shorter previews on blog paginated lists. [00:08:29.008] Tip: turn this security off with the onUntruncatedBlogPosts: 'ignore' blog plugin option. [00:08:29.605] [info] [webpackbar] Compiling Client [00:08:29.640] [info] [webpackbar] Compiling Server [00:08:41.004] [success] [webpackbar] Server: Compiled successfully in 11.36s [00:08:52.361] [success] [webpackbar] Client: Compiled with some errors in 22.76s [00:08:52.366] [ERROR] Client bundle compiled with errors therefore further build is impossible. [00:08:52.367] Syntax error: /vercel/path0/src/pages/our-sponsors/Sponsors.css Unclosed block (621:1) [00:08:52.367] [00:08:52.367] �[90m 619 | �[39m line-height�[33m:�[39m 1.6�[33m;�[39m [00:08:52.367] �[90m 620 | �[39m�[33m}�[39m [00:08:52.367] �[1m�[31m>�[39m�[22m�[90m 621 | �[39m�[33m[�[39mdata-theme=�[32m'dark'�[39m�[33m]�[39m �[33m.scanner-content�[39m �[33m{�[39m [00:08:52.367] �[90m | �[39m�[1m�[31m^�[39m�[22m [00:08:52.367] �[90m 622 | �[39m background�[33m:�[39m �[36mvar�[39m�[36m(--dark-bg-secondary)�[39m�[33m;�[39m [00:08:52.368] �[90m 623 | �[39m color�[33m:�[39m �[36mvar�[39m�[36m(--dark-text-primary)�[39m�[33m;�[39m [00:08:52.368] [00:08:52.368] -------------------------- [00:08:52.368] [00:08:52.368] Syntax error: /vercel/path0/src/pages/our-sponsors/Sponsors.css Unclosed block (621:1) [00:08:52.368] [00:08:52.368] �[90m 619 | �[39m line-height�[33m:�[39m 1.6�[33m;�[39m [00:08:52.368] �[90m 620 | �[39m�[33m}�[39m [00:08:52.368] �[1m�[31m>�[39m�[22m�[90m 621 | �[39m�[33m[�[39mdata-theme=�[32m'dark'�[39m�[33m]�[39m �[33m.scanner-content�[39m �[33m{�[39m [00:08:52.368] �[90m | �[39m�[1m�[31m^�[39m�[22m [00:08:52.368] �[90m 622 | �[39m background�[33m:�[39m �[36mvar�[39m�[36m(--dark-bg-secondary)�[39m�[33m;�[39m [00:08:52.368] �[90m 623 | �[39m color�[33m:�[39m �[36mvar�[39m�[36m(--dark-text-primary)�[39m�[33m;�[39m [00:08:52.368] -- inner error -- [00:08:52.368] [00:08:52.368] Syntax error: /vercel/path0/src/pages/our-sponsors/Sponsors.css Unclosed block (621:1) [00:08:52.368] [00:08:52.368] �[90m 619 | �[39m line-height�[33m:�[39m 1.6�[33m;�[39m [00:08:52.368] �[90m 620 | �[39m�[33m}�[39m [00:08:52.369] �[1m�[31m>�[39m�[22m�[90m 621 | �[39m�[33m[�[39mdata-theme=�[32m'dark'�[39m�[33m]�[39m �[33m.scanner-content�[39m �[33m{�[39m [00:08:52.369] �[90m | �[39m�[1m�[31m^�[39m�[22m [00:08:52.369] �[90m 622 | �[39m background�[33m:�[39m �[36mvar�[39m�[36m(--dark-bg-secondary)�[39m�[33m;�[39m [00:08:52.369] �[90m 623 | �[39m color�[33m:�[39m �[36mvar�[39m�[36m(--dark-text-primary)�[39m�[33m;�[39m [00:08:52.369] Generated code for /vercel/path0/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[7].use[1]!/vercel/path0/node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[7].use[2]!/vercel/path0/src/pages/our-sponsors/Sponsors.css [00:08:52.443] Error: Command "npm run build" exited with 1

check the comments once @sanjay-kv , its important

sanjay-kv · 2025-09-02T17:15:54Z

@Adez017

your thought on this is good, even im having a rethought of bringing back the old design as that was more User friendly in the look and feel. we can bring back the old UI

Adez017 · 2025-09-02T17:21:12Z

@Adez017

your thought on this is good, even im having a rethought of bringing back the old design as that was more User friendly in the look and feel. we can bring back the old UI

would i do that or you will do at your end? @sanjay-kv

Adez017 · 2025-09-02T17:21:53Z

if the old UI is backed we can have this changes

sanjay-kv · 2025-09-02T17:23:09Z

Can u bring back the change in new PR or something. @Adez017 once that's done we can merge this current PR. Meanwhile I will sponsor u on 15th of sept

Adez017 · 2025-09-02T17:29:58Z

Can u bring back the change in new PR or something. @Adez017 once that's done we can merge this current PR. Meanwhile I will sponsor u on 15th of sept

got it , ill be making a new PR with revert chnages .👍, thanks for the sponsorship in advance 😁

Fixed visiblity of text on teh sponsors page dark mode

4745422

iitzIrFan added this to @recode-web Aug 29, 2025

iitzIrFan moved this to Done in @recode-web Aug 29, 2025

iitzIrFan moved this from Done to In Progress in @recode-web Aug 29, 2025

iitzIrFan added the under review Review under the maintainers or the admins label Aug 29, 2025

iitzIrFan assigned Adez017 Aug 29, 2025

iitzIrFan requested changes Aug 29, 2025

View reviewed changes

iitzIrFan self-requested a review August 30, 2025 12:11

iitzIrFan approved these changes Aug 30, 2025

View reviewed changes

iitzIrFan requested a review from sanjay-kv August 30, 2025 12:12

sanjay-kv approved these changes Sep 2, 2025

View reviewed changes

vercel bot deployed to Preview September 2, 2025 12:51 View deployment

Adez017 mentioned this pull request Sep 2, 2025

💡[Feature]: Add a rolling number effects on landing page footer #466

Closed

4 tasks

sanjay-kv approved these changes Sep 2, 2025

View reviewed changes

Merge branch 'main' into docs

a123b89

vercel bot had a problem deploying to Preview September 2, 2025 17:08 Failure

sanjay-kv closed this Sep 6, 2025

github-project-automation bot moved this from In Progress to Done in @recode-web Sep 6, 2025

Adez017 deleted the docs branch September 6, 2025 12:48

Fixed visiblity of text on teh sponsors page dark mode #464

Fixed visiblity of text on teh sponsors page dark mode #464

Uh oh!

Conversation

Adez017 commented Aug 29, 2025

Description

Type of Change

Changes Made

Dependencies

Checklist

Uh oh!

vercel bot commented Aug 29, 2025

Uh oh!

github-actions bot commented Aug 29, 2025

Uh oh!

iitzIrFan left a comment

Choose a reason for hiding this comment

Uh oh!

Adez017 commented Aug 30, 2025

Uh oh!

iitzIrFan left a comment

Choose a reason for hiding this comment

Uh oh!

Adez017 commented Sep 2, 2025

Uh oh!

iitzIrFan commented Sep 2, 2025

Uh oh!

sanjay-kv left a comment

Choose a reason for hiding this comment

Uh oh!

vercel bot commented Sep 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Adez017 commented Sep 2, 2025

Uh oh!

sanjay-kv commented Sep 2, 2025

Uh oh!

Adez017 commented Sep 2, 2025

Uh oh!

Adez017 commented Sep 2, 2025

Uh oh!

sanjay-kv commented Sep 2, 2025

Uh oh!

Adez017 commented Sep 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Adez017 commented Sep 2, 2025

Uh oh!

sanjay-kv commented Sep 2, 2025

Uh oh!

Adez017 commented Sep 2, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

vercel bot commented Sep 2, 2025 •

edited

Loading

Adez017 commented Sep 2, 2025 •

edited

Loading